provider/kubernetes: Add support for persistent_volume #13277
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sorry for the 2,4k LOC 🙈 , but vast majority of it is the schema & related expanders/flatteners.
Test plan
I avoided writing tests for every single volume source provider for two reasons - avoid ⬆️ LOC and because K8S API doesn't seem to care about anything except optional/required fields. That is also why most of the configs have non-sense volume IDs etc. which don't exist. I suspect K8S would only failed to schedule a pod with such volume - i.e. it is just postponing the error/validation to latest moment.
I did try to create PV for each volume source provider manually though and that worked 👌 .